User Guide

Build a beautiful landing page
in under an hour

Fill in your content, choose your colors, click Generate. The tool writes the code — you just add your photos and upload.

Overview

How this tool works

The Landing Page Builder uses your Anthropic API key to send your content to Claude, which writes a complete, production-ready HTML page. You preview it in the tool, download it, add your photos, and upload everything to your server. No coding required.

1
Enter your API key

Your key connects the tool to Claude. It's saved in your browser only — it never leaves your computer.

2
Fill in the form sections

Your business info, colors, copy for each section of the page. Take your time — better content produces a better page.

3
Click Generate

Claude writes the full HTML page (~30 seconds). A live preview appears on the right.

4
Download the ZIP

You get an index.html file and an images/ folder with a README explaining exactly which photos to add.

5
Add your photos and upload

Name your photos exactly as specified, drop them in the images/ folder, and upload everything to your server. Done.


Step 1

Getting your Anthropic API key

You need an Anthropic API key to use this tool. Getting one takes about two minutes.

1
Go to console.anthropic.com

Create a free account or sign in.

2
Open API Keys in the left sidebar

Click "Create Key," give it a name (e.g. "Landing Page Builder"), and copy the key.

3
Add credits to your account

Go to Billing and add a small amount — $5–10 is plenty to start. Each page generation costs roughly $0.10–0.20 depending on the model you choose.

4
Paste the key into the tool

Open the Landing Page Builder, paste your key into the API Key field at the top. It saves automatically — you'll see "● Saved" appear. You won't need to enter it again.

Your key is private. It's stored only in your browser's local storage. It never goes to any server other than Anthropic's own API. Don't share the tool's HTML file with your key already filled in — anyone who opens it could use your account.

Choosing a model

Three Claude models are available. The model you choose affects cost and quality:

Haiku 4.5 — Fast and inexpensive. Good for testing your content. Sonnet 4.6 — Balanced speed and quality. Recommended for final output. Opus 4.8 — Most capable. Best for complex or unusual design requests.

Start with Haiku while you're filling in your content and iterating. Switch to Sonnet or Opus for your final generation.


Step 2

Filling in the form sections

Each collapsible section covers one part of your page. Click any section header to collapse it after you've filled it in, keeping the form manageable.

🏢 Your Business

The foundation of the whole page. Your business name appears in the navigation bar as a fallback if no logo is provided. The tagline and business type help Claude understand the right tone and visual approach for the design.

Website URL appears as a link in the footer. Email address is rendered as a clickable mailto: link in both the bio section and the footer.

🎨 Color & Style

Primary color is used for backgrounds, the nav bar when it's solid, and dark overlays on hero/footer images. Accent color is used for buttons, links, highlights, and decorative elements.

The Page Theme sets the overall feel: Dark & Moody uses near-black backgrounds; Light & Clean uses whites and light greys; Warm Neutral uses creams and off-whites. The Font Style guides Claude to choose appropriate Google Fonts — Elegant Serif picks typefaces like Cormorant or Playfair; Modern Sans picks something like DM Sans or Plus Jakarta Sans.

Tip: If you have specific fonts in mind, mention them in the Design Instructions section (design.md). For example: "Use Cormorant Garamond for headings and Lato for body text."

✨ Hero Section

The first thing visitors see — a full-screen section with your background photo, a headline, subheadline, and a call-to-action button. The CTA Button Link is where the button sends visitors when clicked. This is typically your contact page or booking form URL.

Write the headline as a short, punchy statement (5–8 words). The subheadline can be 1–2 sentences expanding on it.

👤 About / Bio

A two-column section: your photo on the left, bio text on the right. The Section Headline is the large text above your bio — something personal like "Hi, I'm Sarah" or "About the Studio" works well. Write 2–4 sentences for the bio itself. Keep it conversational and specific — tell people who you are and why you do what you do.

🃏 Feature Cards

Three cards in a row, each with a photo, title, and short description. Use these for your main services or areas of work. The Section Headline ("What I Do Best", "Services", "My Work") sits above the grid.

Keep each card description to 2–3 sentences. Specific is better than general: "60-minute in-studio sessions for individuals and couples" is stronger than "professional portraits."

Important: All three card images must be the same dimensions. If card1.jpg is 800×500px, card2 and card3 must also be 800×500px. Mismatched sizes create an uneven grid.

📣 Mid-Page CTA

A side-by-side section that breaks up the page and drives visitors toward action — your copy on the left, a square photo on the right. The Button Link can be your contact page, a booking form, or any deep link on your site. Write the body text as a personal, direct invitation: 2–3 sentences.

💬 Testimonials

Three client quotes. Keep quotes to 1–3 sentences — short quotes read better than long ones. Include the client's name and a brief role or context ("Wedding Client, 2024" or "Founder, Bloom Studio").

📱 Social Media

Paste the full URL for any platform you want to appear. Leave a field blank and that platform won't show up anywhere on the page. All four are completely optional.

📌 Footer

The footer uses your footer photo as a background with a dark overlay. The Footer Headline is typically a final call to action — "Ready to work together?" or "Let's make something great."

The Bottom Link is useful if this landing page is separate from your main site — it gives visitors a way to see your full portfolio or navigate elsewhere. It can also be a deep link: a specific gallery, your booking calendar, or a project page.


Step 3

Preparing your images

The generated page references eight image files by exact filename. You never need to edit the HTML — just name your photos correctly and drop them in the images/ folder.

images/logo.png
Your logo in the nav bar
Max 400 × 120px
PNG with transparent background strongly recommended. If missing, your business name appears as text.
images/hero.jpg
Full-screen hero background
1920 × 1080px
Landscape orientation. Choose a strong, atmospheric image — it covers the whole screen.
images/bio.jpg
About / bio section photo
600 × 750px
Portrait orientation works best here — taller than wide. A headshot or environmental portrait.
images/card1.jpg
Feature card 1 image
800 × 500px
Must match card2 and card3 exactly.
images/card2.jpg
Feature card 2 image
800 × 500px
Must match card1 and card3 exactly.
images/card3.jpg
Feature card 3 image
800 × 500px
Must match card1 and card2 exactly.
images/cta.jpg
Mid-page CTA image
600 × 600px
Square format. A close detail shot, workspace, or behind-the-scenes image works well.
images/footer.jpg
Footer background
1920 × 600px
Wide landscape crop. Subject matter is less important since a dark overlay covers most of it.
Swapping images later is easy. Since every image uses object-fit: cover, replacing a file in the images/ folder is all you need to do. No code editing, ever. The layout stays perfect regardless of the exact file you put in.

Compressing your images

Large image files slow down your page. Before uploading, run your images through a compression tool. Target under 400KB per file — most will compress to far less without visible quality loss.

Good free tools: Squoosh (squoosh.app) for individual images, TinyPNG (tinypng.com) for batch compression. For the logo, export from your design app as a compressed PNG with transparency.


Optional but powerful

Using a design.md file

The Design Instructions section lets you give Claude additional guidance beyond what the form covers. Think of it as a short creative brief — you can steer the layout, typography, tone, spacing, or anything else about the design.

You can either paste directly into the textarea, or click Load .md file to load a text file you've already written. The content supplements your form inputs — it doesn't override your color or font choices.

What to put in it

Write it as plain notes, one idea per line. You don't need any special formatting. Some examples of useful instructions:

# Design preferences - Prefer asymmetric layouts over centered grids - Avoid drop shadows — use subtle borders instead - Use Cormorant Garamond for headings, DM Sans for body text - Hero overlay: keep it minimal so the image breathes - Cards: rounded corners (12px), no border # Tone of voice - Copy should feel direct and confident, never flowery - Use short sentences. Avoid filler phrases. # Section-specific - Testimonials: lead with the client name, quote below - Bio section: image on the right, not the left - Nav: add anchor links — Work · About · Contact
Keep it focused. 10–15 specific instructions produce better results than a long essay. Claude reads and applies every line — the more specific you are, the more precisely it reflects your vision.

You can save your design.md file and reuse it across multiple page generations. It's a fast way to maintain consistency if you're building pages for multiple clients.


Step 4

Generating and previewing

Once your form is filled in, click Generate My Landing Page at the bottom of the form. Claude writes a complete HTML document — typically 6,000–8,000 characters of code — which takes about 30 seconds.

A character counter in the center of the preview area increments as the page is built. When it's done, the live preview loads automatically on the right side of the screen.

About the preview

The preview is a real, fully rendered HTML page inside an iframe. You can scroll it, check the layout, and read all the content. The images will appear as broken image icons — that's expected, since the photo files aren't loaded in the preview. The layout, colors, typography, and copy are all accurate.

Not happy with the result? Adjust your form inputs — more specific copy, different colors, or additional design instructions — and click Generate again. Each generation is independent, so you can iterate as many times as you like. Using Haiku for test runs keeps costs low while you refine your content.

Downloading your files

Two download options appear after generation:

HTML Only

Downloads just the index.html file. Use this if you already have your images ready and just need the HTML.

ZIP + Images Folder

Downloads a .zip file containing index.html and an images/ folder with a README. The README lists every image filename, the recommended dimensions, and deployment instructions. Recommended for first-time use.


Step 5

Deploying your page

Once you have your files and images ready, putting the page live takes just a few minutes.

1
Unzip the downloaded file

You'll see index.html and an images/ folder. The images folder contains only a README at this point.

2
Add your photos to the images/ folder

Name each file exactly as specified (see the Images section above). Compress them first if you haven't already.

3
Preview locally before uploading

Open index.html in your browser from your computer. The page should look complete with all images showing. Check on mobile too — resize your browser window to a narrow width.

4
Upload to your server

Use FTP, your hosting control panel, or your host's file manager. Upload index.html and the entire images/ folder to the same location. If this is your homepage, upload to the root of your domain.

5
Visit the live URL

Open your site in a browser. If everything looks correct locally, it will look correct live.

Page not showing images? The most common issue is a folder structure mismatch. The images/ folder must be in the same directory as index.html — not inside a subfolder of it, and not one level above it.

Best practices

Tips for great results

✍️
Write real copy first
Don't use placeholder text. The more specific and genuine your content, the better the page. Claude writes better design decisions when the copy is real.
🎨
Test colors before committing
Run a quick Haiku generation with your color choices to see how they look. Adjust and regenerate — it only costs a few cents per test.
📐
Match your card image sizes exactly
All three card images must be the same dimensions. Resize them in Lightroom, Photoshop, or any image editor before exporting.
📋
Build a reusable design.md
Save your design preferences to a design.md file and reuse it across multiple generations or client projects. It's the fastest way to keep a consistent style.
📱
Always check mobile
The generated page is fully responsive, but always test it. Resize your browser to 375px wide and scroll the whole page before uploading.
Compress every image
Run all photos through Squoosh or TinyPNG before uploading. A well-compressed page loads in under 2 seconds — uncompressed images can make it 10× slower.

FAQ

Common questions

How much does each generation cost?
With Sonnet 4.6 (recommended), expect roughly $0.10–0.20 per generation. Haiku is about 10× cheaper for testing. Opus costs more but produces noticeably more creative designs for complex requests.
Can I edit the generated HTML?
Yes. The output is standard, readable HTML and CSS — no frameworks, no minification. Open it in any code editor and change whatever you need. Or regenerate with updated form inputs.
My logo isn't showing up on the live page.
Check that your file is named exactly images/logo.png (lowercase, .png extension) and is in the images/ folder at the same level as index.html. If no logo file is present, the business name text shows automatically instead.
Can I use this for client work?
Yes. Each client uses their own API key (or you can use yours and factor the cost into your fee). The generated HTML belongs to you completely — there's no license or attribution requirement.
Can I add more sections or change the layout?
Use the Design Instructions (design.md) section to request layout changes — "add a fourth card," "put the bio section after testimonials," "add an FAQ section." Claude will apply them in the next generation. For major structural changes, editing the HTML directly is faster.
The page looks different in Safari vs Chrome.
The generated page uses standard CSS that works across all modern browsers. If you spot a difference, it's usually a font rendering or line-height variation — minor and normal. Test in both before publishing.
Can I run this tool offline?
The tool requires an internet connection to call the Anthropic API and to load Google Fonts. Everything else — the form, the preview, the downloads — runs entirely in your browser.